-
Notifications
You must be signed in to change notification settings - Fork 876
[WIP] Inconsistencies and improvements to SST model #2329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
- Added production terms to SST
- Added user-defined production limiter constant for TKE
- Updated boundary conditions as in TMR page
Common/include/CConfig.hpp
Outdated
nPrandtl_Lam, /*!< \brief Number of species | ||
addDoubleOption("FREESTREAM_TURB2LAMVISCRATIO", TurbIntensityAndViscRatioFreeStream[1], 10.0); Prandtl number. */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this intentionally commented, or...? If it is used, I guess this should go to line 872
nPrandtl_Lam, /*!< \brief Number of species | |
addDoubleOption("FREESTREAM_TURB2LAMVISCRATIO", TurbIntensityAndViscRatioFreeStream[1], 10.0); Prandtl number. */ | |
nPrandtl_Lam, /*!< \brief Number of species laminar Prandtl number. */ | |
addDoubleOption("FREESTREAM_TURB2LAMVISCRATIO", TurbIntensityAndViscRatioFreeStream[1], 10.0); /*!<\brief Freestream mu_turb to mu_lam viscosity ratio */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just a wrong copy-paste from me. It should not be there in the first place.
Great contribution, Thanks @rois1995 ! |
If you are looking into robustness aspects too you should get in touch with @emaberman and @YairMO, seems like they have some good ideas and between the free time of 3 people a lot more can get done :) |
Hi, Regarding the cross-diffusion term (CD) that appears in Omega source term (residual). The SST model (1994/2003) is a high-Reynolds-number model. Namely, It can not predict correctly the sub-layer region (especially the correct profile of the TKE). Therefore, only a positive contribution is required. Moreover, since the SST model was design as a k-w and k-epsilon blending, the CD term "belongs" only to the k-epsilon "branch", that is why the CD term include the factor "1-F1". However, it may happen, that the factor "1-F1" is not a 100% safe guarantee. It may happen that "1-F1" is not zero in region where the CD term is negative (this happen due numerical errors). To avoid such a situation, it is a good idea to clip the CD term with zero. Otherwise, severe numerical robustness issues may rise. |
- Given option for cross diffusion limiting in W residual
Hi, The use of an Omega production limiter (about the cross-diffusion term) is correct for low-Reynolds-number (LRN) models (the approach described by Peng et al. is very naive; there are other more rigorous treatments). For high-Reynolds-number (HRN) models, the clipping should be zero, keeping the cross-diffusion term positive; thus, the current implementation is correct. Indeed, it is not exactly as it appears in Menter's original publication. The factor (1-F1) aimed to promise that the cross-diffusion term will be activated only outside the boundary layer, where it is positive (the cross-diffusion term switches its sign deep inside the boundary layer). This was also recognized by Peng et al. (first paragraph above Eq. 17). However, it may happen that the factor (1-F1)=1 where the cross-diffusion term is negative. Usually, it may happen at the wake, very near the airfoil trailing edge, where the upper and lower boundary layers merge. It is due to the imperfection of the F1 function. To summarize, the current implementation is correct, and it is perfect for HRN models. |
For the sake of clarity, "current implementation" refers to the current treatment of the production code |
What YairMO is saying, is that allowing negative cross diffusion values is incorrect for high Reynolds models and should not be an option, this is a fix used for low Reynolds models only |
Hi @YairMO, Hi @emaberman , thank you very much for your comments. I haven't found any suggestion in literature to clip to only positive values the cross-diffusion term in the w-equation. I understand that it might be more robust, but it is not the standard implementation of the SST model, which is the first thing that we need to achieve. Only then we can build on top of that to improve the robustness of SU2. Nevertheless, I tried the SWBLI test case and I compared the results across 6 different combinations: 1- develop branch, no changes When my branch is used, then the changes to the supersonic inlet BC are already in place. I haven't achieved convergence with 1, 2 and 3. More precisely, 1 diverged right away (after 30 iterations), while 2 and 3 gave "FGMRES - Orthogonalization Failed" after 900ish iterations. Here you can see the residuals for the different combinations. Unfortunately I will be busy with the AIAA Conference next week, thus I don't know how much I will be able to work on this. The next test case will be the 2D airfoil near-wake from TMR. |
Hi rois1995, First of all, enjoy your time in Las Vegas. Any paper that you are presenting? As for our discussion about the cross-diffusion term, I've emailed the "source" (Menter). I believe he will make it clear. |
Common/include/CConfig.hpp
Outdated
@@ -865,7 +865,7 @@ class CConfig { | |||
nMu_Temperature_Ref, /*!< \brief Number of species reference temperature for Sutherland model. */ | |||
nMu_S, /*!< \brief Number of species reference S for Sutherland model. */ | |||
nThermal_Conductivity_Constant,/*!< \brief Number of species constant thermal conductivity. */ | |||
nPrandtl_Lam, /*!< \brief Number of species laminar Prandtl number. */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original description was correct, for species transport we can have a Prandtl number for each of the species
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I do not recall changing that but for sure it was wrong in my branch. Corrected, thanks!
su2double Omega_Freestream = 10 * ModVel_FreeStream / config->GetLDomain(); | ||
Tke_FreeStream = Omega_Freestream*(Viscosity_FreeStream*config->GetTurb2LamViscRatio_FreeStream())/Density_FreeStream; | ||
} else if (config->GetSSTParsedOptions().sust) { | ||
su2double Omega_Freestream = 5*ModVel_FreeStream/config->GetLength_Reynolds(); |
Check notice
Code scanning / CodeQL
Unused local variable Note
Co-authored-by: Nijso <[email protected]>
* \param[in] iPoint - Point index. | ||
* \return Value of magnitude. | ||
*/ | ||
inline virtual su2double GetStrainMag(unsigned long iPoint) const {} |
Check failure
Code scanning / CodeQL
Missing return statement Error
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 3 months ago
To fix the problem, we need to ensure that all execution paths in the function GetStrainMag
return a value of type su2double
. Since this is a virtual function, the base class implementation can return a default value, such as 0.0
, which is a common practice for numerical functions. This will ensure that the function has a defined return value even if it is not overridden by derived classes.
-
Copy modified line R1394 -
Copy modified line R1400
@@ -1393,3 +1393,3 @@ | ||
*/ | ||
inline virtual su2double GetStrainMag(unsigned long iPoint) const {} | ||
inline virtual su2double GetStrainMag(unsigned long iPoint) const { return 0.0; } | ||
|
||
@@ -1399,3 +1399,3 @@ | ||
*/ | ||
inline virtual su2activevector& GetStrainMag() {} | ||
inline virtual su2activevector& GetStrainMag() { static su2activevector default_vector; return default_vector; } | ||
|
* \brief Get the entire vector of the rate of strain magnitude. | ||
* \return Vector of magnitudes. | ||
*/ | ||
inline virtual su2activevector& GetStrainMag() {} |
Check failure
Code scanning / CodeQL
Missing return statement Error
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 3 months ago
To fix the problem, we need to ensure that the function GetStrainMag
returns a value of type su2activevector&
. Since this is a virtual function, it is likely that derived classes will provide the actual implementation. However, we still need to provide a valid return value in the base class to avoid undefined behavior.
The best way to fix this issue without changing existing functionality is to return a reference to a static instance of su2activevector
. This ensures that the function returns a valid reference, and it avoids the need to modify the function's signature or the class's interface.
-
Copy modified lines R1400-R1403
@@ -1399,4 +1399,6 @@ | ||
*/ | ||
inline virtual su2activevector& GetStrainMag() {} | ||
|
||
inline virtual su2activevector& GetStrainMag() { | ||
static su2activevector dummy; | ||
return dummy; | ||
} | ||
/*! |
…feature_SSTMod
// su2double MeanReynoldsStress[3][3]; | ||
// ComputeStressTensor(nDim, MeanReynoldsStress, PrimVar_Grad_i + idx.Velocity(), Eddy_Viscosity_i, | ||
// Density_i, ScalarVar_i[0]); |
Check notice
Code scanning / CodeQL
Commented-out code Note
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI about 2 months ago
The best way to fix the problem is to remove the commented-out code entirely. This will make the code cleaner and easier to read, and it will eliminate any potential confusion about the commented-out sections. If the code is needed for future reference, it should be documented separately or added to version control comments.
- Remove the commented-out code from lines 869 to 879.
- Ensure that the remaining code is properly formatted and that no functionality is lost.
@@ -867,16 +867,3 @@ | ||
case SST_OPTIONS::COMP_ShuzHoff:{ | ||
|
||
// su2double MeanReynoldsStress[3][3]; | ||
// ComputeStressTensor(nDim, MeanReynoldsStress, PrimVar_Grad_i + idx.Velocity(), Eddy_Viscosity_i, | ||
// Density_i, ScalarVar_i[0]); | ||
|
||
// for (size_t iDim = 0.0; iDim < nDim; iDim++){ | ||
// for (size_t jDim = 0.0; jDim < nDim; jDim++){ | ||
// PDTerm += MeanReynoldsStress[iDim][jDim] * PrimVar_Grad_i[idx.Velocity() + iDim][jDim]; | ||
// } | ||
// } | ||
// PDTerm = (-alpha2*PDTerm + alpha3 * epsilon * Density_i)*Mt*Mt; | ||
|
||
zetaFMt = alpha1 * Mt*Mt * (1-F1_i); | ||
|
||
P_Base = StrainMag_i; |
// for (size_t iDim = 0.0; iDim < nDim; iDim++){ | ||
// for (size_t jDim = 0.0; jDim < nDim; jDim++){ | ||
// PDTerm += MeanReynoldsStress[iDim][jDim] * PrimVar_Grad_i[idx.Velocity() + iDim][jDim]; | ||
// } | ||
// } | ||
// PDTerm = (-alpha2*PDTerm + alpha3 * epsilon * Density_i)*Mt*Mt; |
Check notice
Code scanning / CodeQL
Commented-out code Note
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI about 2 months ago
To fix the problem, we should remove the commented-out code entirely. This will make the code cleaner and easier to read, and it will eliminate any potential confusion about whether the commented-out code is meant to be re-enabled or not.
- Locate the commented-out code block starting at line 869 and ending at line 878.
- Remove the entire block of commented-out code.
- Ensure that the remaining code is properly formatted and that no functionality is lost.
@@ -867,16 +867,3 @@ | ||
case SST_OPTIONS::COMP_ShuzHoff:{ | ||
|
||
// su2double MeanReynoldsStress[3][3]; | ||
// ComputeStressTensor(nDim, MeanReynoldsStress, PrimVar_Grad_i + idx.Velocity(), Eddy_Viscosity_i, | ||
// Density_i, ScalarVar_i[0]); | ||
|
||
// for (size_t iDim = 0.0; iDim < nDim; iDim++){ | ||
// for (size_t jDim = 0.0; jDim < nDim; jDim++){ | ||
// PDTerm += MeanReynoldsStress[iDim][jDim] * PrimVar_Grad_i[idx.Velocity() + iDim][jDim]; | ||
// } | ||
// } | ||
// PDTerm = (-alpha2*PDTerm + alpha3 * epsilon * Density_i)*Mt*Mt; | ||
|
||
zetaFMt = alpha1 * Mt*Mt * (1-F1_i); | ||
|
||
P_Base = StrainMag_i; |
Proposed Changes
Hi everyone,
I have found some inconsistencies with respect to the literature on the implementation of the Menter's SST model. I would like to use this branch as test bench for any corrections/improvements made to the SST model.
Implementation errors found:
positive portion of the cross-diffusion term in Eq (A2)" pag. 1604. Moreover, a clipping has been introduced for large negative values of this term, as suggested in Peng, Shia-Hui, Peter Eliasson, and Lars Davidson. "Examination of the shear stress transport assumption with a low-Reynolds number k-omega model for aerodynamic flows." Eq 17.
Changes to SST model proposed:
I've seen the proposed changes to the lower limits of k and w in #2323 and I tried implementing it in my branch. However, if the implementation proposed in the respective PR is preferred then I will change mine.
Related Work
#2323 #1851
PR Checklist
Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.
pre-commit run --all
to format old commits.